Dynamic Joint Dividers for Application Windows

ABSTRACT

This document describes techniques and apparatuses enabling dynamic joint dividers for application windows. In some embodiments, these techniques and apparatuses enable sizing and positioning of application windows to provide an optimized layout of application windows.

BACKGROUND

This background is provided for the purpose of generally presenting acontext for the instant disclosure. Unless otherwise indicated herein,material described in the background is neither expressly nor impliedlyadmitted to be prior art to the instant disclosure or the claims thatfollow.

Conventional operating systems permit users to view multiple computingapplications through windows. Each of these windows generally includes aframe or control for selecting which window is primary or to move, size,or otherwise manage placement of the window with respect to a workspaceand other windows. These frames or controls, however, often only enablea currently selected window to be moved or sized, which can result inunintended occlusion and overlap between the windows. Additionally,moving or sizing multiple windows often requires a user to perform aseries of redundant tasks to iteratively move or size each window asdesired. As such, managing the layout of multiple windows in thisfashion can be overly complicated, time-consuming, and annoying tousers.

SUMMARY

This document describes techniques and apparatuses enabling dynamicjoint dividers for application windows in a multi-applicationenvironment. The multi-application environment described herein presentsone or more application windows, which can be sized, positioned, orlayered to provide an optimized layout. In some embodiments, thesetechniques and apparatuses enable a size or position of an applicationwindow to be determined based on an edge of another application window.Also, in some embodiments the techniques and apparatuses enable anapplication window to be sized to a predefined area based on selectionof a region of the multi-application environment. Further still, someembodiments enable joint dividers or joint corner controls, which enablemultiple application windows to be sized or positioned simultaneously.Further, some embodiments identify available regions of amulti-application environment and enable selection of applicationwindows to present via the available region.

This summary is provided to introduce simplified concepts that arefurther described below in the Detailed Description. This summary is notintended to identify essential features of the claimed subject matter,nor is it intended for use in determining the scope of the claimedsubject matter. Techniques and/or apparatuses enabling dynamic jointdividers for application windows are also referred to herein separatelyor in conjunction as the “techniques” as permitted by the context,though techniques may include or instead represent other aspectsdescribed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments enabling a multi-application environment are described withreference to the following drawings. The same numbers are usedthroughout the drawings to reference like features and components:

FIG. 1 illustrates an example system in which techniques enablingdynamic joint dividers for application windows can be implemented.

FIG. 2 illustrates an example tablet computing device having atouch-sensitive display presenting an immersive interface.

FIG. 3 illustrates a method sizing or position a window of anapplication to fill a region of a multi-application environment.

FIG. 4 illustrates example layouts for regions of a multi-applicationenvironment.

FIG. 5 illustrates a method for sizing and positioning an applicationwindow based on other application windows of a multi-applicationenvironment.

FIG. 6 illustrates examples of sizing and/or positioning applicationwindows for presentation in a multi-application environment.

FIG. 7 illustrates additional examples presenting sizing and/orpositioning application windows for presentation in a multi-applicationenvironment.

FIG. 8 illustrates examples of re-sizing snapped application windows invarious regions of a multi-application environment.

FIG. 9 illustrates a method for sizing an application window based on aregion of a multi-application environment.

FIG. 10 illustrates example selection areas associated with variousregions of a multi-application environment.

FIG. 11 illustrates a method for selecting a region of amulti-application environment based on a state of an application window.

FIG. 12 illustrates an example state machine for implementing the methodof FIG. 12.

FIG. 13 illustrates example drop areas of a multi-applicationenvironment.

FIG. 14 illustrates a method for simultaneously sizing multipleapplication windows using a joint divider.

FIG. 15 illustrates example joint dividers established between variousapplication windows.

FIG. 16 illustrates presentation of a joint control divider inaccordance with one or more embodiments.

FIG. 17 illustrates an example of sizing application windows using ajoint divider.

FIG. 18 illustrates a method for re-sizing an application window whilemoving another application window.

FIG. 19 illustrates an example application of the method of FIG. 18,including an eviction of an application window to another layer of amulti-application environment.

FIG. 20 illustrates example joint dividers that can be establishedbetween application windows.

FIG. 21 illustrates example of joint corners that can be establishedbetween application windows.

FIG. 22 illustrates detailed examples of a joint divider and applicationwindow edges.

FIG. 23 illustrates detailed examples of contiguous and non-contiguousapplication window edges.

FIG. 24 illustrates a method for enabling selection of an applicationwindow for presentation in an available region.

FIG. 25 illustrates an example multi-application environment having anavailable region to present an application window.

FIG. 26 illustrates a method for presenting a selected applicationwindow in an available region.

FIG. 27 illustrates example an application window layouts created byselecting application windows.

FIG. 28 illustrates an example device in which techniques enabling amulti-application environment can be implemented.

DETAILED DESCRIPTION Overview

This document describes techniques and apparatuses enabling dynamicjoint dividers for application windows. These apparatuses and techniquesmay enable application windows of a multi-application environment to beconveniently and efficiently positioned or sized to provide optimizedlayouts of application windows. In some embodiments, these techniquesand apparatuses enable a size or position of an application window to bedetermined based on an edge of another application window. Also, in someembodiments the techniques and apparatuses enable an application windowto be sized to a predefined area based on selection of a region of themulti-application environment. Further still, some embodiments enablejoint dividers or joint corner controls, which enable multipleapplication windows to be sized or positioned simultaneously. Further,some embodiments identify available regions of a multi-applicationenvironment and enable selection of application windows to present viathe available region. These and other forms of application windowmanagement are enabled, in some embodiments, through regions orpredefined areas of the multi-application environment. These are but afew examples of many ways in which the techniques enable dynamic jointdividers for application windows, others of which are described below.

Example System

FIG. 1 illustrates an example system 100 in which techniques enablingdynamic joint dividers for application windows can be embodied. System100 includes a computing device 102, which is illustrated with fourexamples: a smart phone computer 104, a tablet computing device 106, alaptop computer 108, and a gaming device 110, though other computingdevices and systems, such as set-top boxes, servers, and netbooks, mayalso be used.

Computing device 102 includes computer processor(s) 112 andcomputer-readable storage media 114 (media 114). Media 114 includes anoperating system 116, multi-application environment module 118,system-interface module 120, input module 122, application(s) 124, eachhaving one or more application user interfaces 126 (application UI(s)126), application manager 128, which includes or has access toapplication queue 130, and window manager 132.

Computing device 102 also includes or has access to one or more displays134 and input mechanisms 136. FIG. 1 illustrates four example displays,which may be separate or integrated with computing device 102. Inputmechanisms 142 may include gesture-sensitive sensors and devices, suchas touch-based sensors and movement-tracking sensors (e.g.,camera-based), as well as mice (free-standing or integral with akeyboard), a stylus, touch pads, accelerometers, and microphones withaccompanying voice recognition software, to name a few. Input mechanisms136 may be separate or integral with displays 134; integral examplesinclude gesture-sensitive displays with integrated touch-sensitive ormotion-sensitive sensors.

Operating system 116 manages resources of computing device 102 and maybe implemented using any suitable instruction format, such as 64-bit,32-bit, reduced instruction set computing (RISC), complex instructionset computing (CISC), and the like. In some cases, operating system 116may enable execution of a module or application having a differentinstruction format through virtualization. Operating system 116 enablesother modules of computing device 102 to access the resources ofcomputing device 102, such as multi-application environment module 118and applications 124.

Multi-application environment module 118 provides a multi-applicationenvironment by which a user may view and interact with one or more ofapplications 124 through application UIs 126, which are presented viarespective application windows. In some cases, the multi-applicationenvironment is an overlapping windowing environment or workspace thatenables management or manipulation of a position, size, and/orfront-to-back ordering (collectively, “placement”) of overlappingwindows (e.g., the z-ordering of the windows) or non-overlappingwindows. The ordering or ‘depth’ of each application window in aworkspace can be maintained via a z-stack of multi-applicationenvironment module 118. Typically, primary application or non-occludedapplication windows reside at the top of the z-stack. Other applicationwindows, such as non-primary or occluded application windows reside atpositions deeper in the z-stack. These non-primary application windowsmay overlap or occlude each other based on their respective positionswithin the z-stack.

Multi-application environment module 118 may present application UIs 126through application windows having frames. These frames may providecontrols through which to interact with an application and/or controlsenabling a user to position and size the window. Alternately oradditionally, multi-application environment module 118 may presentapplication UIs 126 through application windows having little or nowindow frame, and/or without presenting visual controls (e.g., permanentcontrols on a window frame or in a window obscuring content).

The multi-application environment enabled by multi-applicationenvironment module 118 can be, but is not required to be, hosted and/orsurfaced without use of a windows-based desktop environment. Thus, insome cases multi-application environment module 118 presents amulti-application environment as an immersive environment and precludesusage of desktop-like displays (e.g., a taskbar). Further still, in someembodiments this multi-application environment is similar to anoperating system in that it is not closeable or capable of beingun-installed. While not required, in some cases this multi-applicationenvironment enables use of all or nearly all of the pixels of a displayby applications within the multi-application environment.

System-interface module 120 provides one or more interfaces throughwhich interaction with operating system 116 is enabled, such as anapplication-launching interface, an application management userinterface (application management UI), a start menu, a control panel, ora system tools or options menu, to name just a few. Input module 122receives input through the application windows, input mechanisms 136, orother controls and affordances of a multi-application environment.

Applications 124 may include any suitable type of application, such asproductivity applications, web browsers, media viewers, navigationapplications, multimedia editing applications, and the like. Operatingsystem 116 or multi-application environment module 118 may supportapplications of varying types or instruction sets natively or viavirtualization. For example, multi-application environment module 118may simultaneously present multiple applications 124 of varying types orinstruction sets, such as 32-bit, 64-bit, run-time environments (e.g.,Java or Silverlight, plug-ins (e.g., Flash), RISC, CISC,run-time-languages, and so on.

Each application 124 includes one or more application UIs 126, whichenables viewing or interaction with content of the application.Application UIs 126 may include predefined properties or preferences(e.g., default values or settings) for presenting an application 124,such as an aspect ratio, maximum size, minimum size, position, primacy,display orientation, and the like. In at least some embodiments,application programming interfaces (APIs) associated with an application124 enable access to the properties or preferences of the application124 or respective application UI 126.

Application manager 128 enables management of applications 124, such aslaunching, switching, and tracking active applications. In some cases,application manager 128 enables relationships between applications to beestablished and maintained, such as applications that are frequentlylaunched, positioned, or used within close proximity to each other.Application manager 128 may also have access to, or maintain,application queue 130, which may include active applications, minimizedapplications, or previously-interacted-with applications. Applicationsof application queue 130 may be organized in any suitable fashion, suchas most-recently-used, most-frequently-used, alphabetically, byapplication association, or by application grouping.

In at least some embodiments, window manager 132 enables techniques thatposition or size application windows to provide an optimized layout ofapplication windows in a multi-application environment. Examples ofthese techniques and layouts of application windows, some of which arepresented based on regions of the multi-application environment, areprovided below, though they are not exhaustive or intended to limit thetechniques described herein.

Any or all of operating system 116, multi-application environment module118, system-interface module 120, input module 122, application(s) 124,application manager 128, and window manager 132 may be implementedseparate from each other or combined or integrated in any suitable form.

Example Methods

Example methods 300, 500, 900, and 1100 address sizing or positioningapplication windows based on another application window or a region of amulti-application environment, example methods 1400 and 1800 addressenabling joint dividers for sizing or positioning application windows,and example methods 2400 and 2600 address presenting an applicationwindow in an available area of a multi-application environment.

The methods described herein may be used separately or in combinationwith each other, in whole or in part. These methods are shown as sets ofoperations (or acts) performed, such as through one or more entities ormodules, and are not necessarily limited to the order shown forperforming the operation. For example, the techniques may present anapplication window in a region of a multi-application environment andautomatically present another application window in another region ofthe multi-application environment. The techniques may also size andposition an application window based on a selected region of amulti-application environment, present the sized application window inthe selected region, and then establish a joint divider that enables theapplication window and another application window contacting theapplication window to be simultaneously resized. Further, the techniquesmay present an application window in a region of a multi-applicationenvironment and then present a prompt of other application windows thatare selectable to fill one or more available regions of themulti-application environment.

FIG. 2 illustrates an example operating environment 200 in which thetechniques described herein can be performed. In this particularexample, tablet computing device 106 presents, via multi-applicationenvironment module 118, multi-application environment 202 via display134. Here, multi-application environment 202, which may also be referredto as a workspace, includes application window 204 and applicationwindow 206, each of which occupy approximately half of multi-applicationenvironment 202 as shown by application window divider 208.

As noted above, application windows may include controls (e.g.,application window 204) that enable the application window to be sized,positioned, minimized, closed, and so on. Alternately, applicationwindows may not include controls (e.g., application window 206), whichenables a user interface or content of an application to fully occupy aregion or an area of multi-application environment 202. It should benoted that application windows without controls may still be sized,positioned, or otherwise manipulated by engaging an edge or contents ofthe application window.

Alternately or additionally, multi-application environment 202 may beimplemented as a desktop, virtual or otherwise, and include a controlarea, which is shown as application management UI 210 or a start menu(not shown). For example, when implemented as a desktop,multi-application environment 202 may provide a windows-based workspacein which application windows can be individually moved, sized, orselected as a primary window (e.g. moved to the top of the z-stack).

Multi-application environment 202 may also provide one or more virtualdesktops through which different sets of application windows can bepresented or accessed. By way of example, a user may configure onevirtual desktop with work-based or productivity application windows andanother virtual desktop with media consumption application windows. Byso doing, the user can interact with two different sets of applicationwindows by switching or pivoting between the two virtual desktops. Insome cases, the user may switch an application window from anothervirtual desktop to a currently selected virtual desktop therebyprecluding the need to pivot between the virtual desktops. In at leastsome embodiments, multi-application environment 202, or a sectionthereof, fully occupies a screen or visible area of a display. As such,edges of multi-application environment 202 may align with respectiveedges of the screen or visible area of the display.

Application management UI 210 enables access to features and functionsof operating system 116, system-interface module 120, or otherapplications 124 of computing device 102. For example, applicationwindows can be launched or switched from application management UI 210.Using the techniques herein, application windows can be efficientlyadded, switched, positioned, sized, or otherwise manipulated inmulti-application environment 202 to provide optimized layouts ofapplication windows.

Adaptive Sizing and Positioning of Application Windows

FIG. 3 depicts method 300 for sizing or positioning an applicationwindow based on another application window, including operationsperformed by windows manager 132 or multi-application environment module118. In portions of the following discussion, reference may be made tosystem 100 of FIG. 1, the operating environment 200 of FIG. 2, and othermethods and example embodiments described elsewhere herein, reference towhich is made for example only.

At 302, a selection of a region of a multi-application environment isreceived. The region can be selected via any suitable input, such as ahot-key combination or directional input received via an applicationwindow (e.g., window dragging). In some cases, selection of the regionis received via an application window being added to, switched to, ormoved within the multi-application environment. The region may includeany suitable section or area of the multi-application environment, suchas a section along an edge of a screen or a section in the center of thescreen. In some cases, a user may define or configure particular areas(e.g., sections or strips of screen area) within the multi-applicationenvironment as user-defined regions.

The region may be fixed, predefined, or dynamic, such as a region thatchanges size or position due to an orientation of a display or type ofinput received. In some cases, a region may be associated with acorresponding operation, such as a “snap” operation, which fills theregion with an application window at a predefined size or predefinedposition. These predefined sizes or predefined positions may correspondto predefined areas of a multi-application environment, which mayinclude horizontal and/or vertical quadrants or fractions of aworkspace, such as halves, quarters, thirds, and any combinationthereof. Alternately or additionally, the predefined areas of themulti-application environment may be defined by a user, such as bypartitioning a workspace or by saving an application window's size,position, or location within a z-stack as a predefined area.

By way of example, consider FIG. 4, which illustrates example workspaces400, 402, and 404, each of which illustrate various layouts of regions.Here, application windows 406, 408, 410, and 412 of workspace 400 areinitially snapped to quadrant areas of the workspace. An applicationwindow may be considered snapped when the application window contacts ortouches two or more adjacent edges of a workspace or screen. Similarly,application windows 414 and 416 are initially snapped to half areas ofworkspace 402.

At 304, an edge of another application window that is adjacent to theselected region is identified. The other application window may occupyan adjacent region of the multi-application environment. In some cases,the edge of the other application window is complimentary to theselected region. Alternately or additionally, an edge of a non-adjacentapplication window may be identified (e.g., complimentary ornon-complimentary).

For example, consider region 418, region 420, and region 422 ofworkspace 404 along axes originating from corner 424. Here, region 418and region 420 are adjacent to corner 424 and region 422 is not adjacentto corner 424. Further, edges of regions may be classified ascomplementary or non-complementary along an individual axis. From corner424 and along an X-axis, edge 426 and edge 428 are complimentary andedge 430 is not complimentary. Similarly, from corner 424 and along aY-axis, edge 432 and edge 434 are complimentary and edge 436 is notcomplimentary.

In the context of workspace 400, assume window 438 is being dragged intoa corner region of workspace 400. Here, window manager 132 identifies anedge of application window 410, which is adjacent to the region intowhich application window 438 is moving. Additionally, in the context ofworkspace 402, application window 440 is being dragged into a sideregion of workspace 402. Here, window manager 132 identifies an edge ofapplication window 416, which is adjacent to the region into whichapplication window 440 is moving.

At 306, a size or a position is determined for the application windowbased on the edge of the other application window. The size or positionof the application window may be determined such that the applicationwindow fills the region to the edge of the other application window. Insome cases, the size or position is determined such that an edge of theapplication window aligns with a complimentary edge of an adjacentapplication window. In such cases, the application window and adjacentapplication window may have a same width or a same height. Alternatelyor additionally, the determined size or position may correspond to apredefined area of a multi-application environment, such as a quadrantarea or half area of a workspace.

Returning to example workspace 400, window manager determines a size forapplication window 438 such that edges of application window 438 alignwith edges of application window 410 and application window 408.Additionally, in the context of workspace 402, window manager determinesa size for application window 440 such that an edge of applicationwindow 440 aligns with the edge of application window 416.

At 308, the application window is presented in the selected region ofthe multi-application environment at the determined size or determinedposition. In some cases, the application window is presented overanother application window occupying the selected regions. In suchcases, the other application window may be relegated to another primacylayer of the multi-application environment (e.g., deeper in thez-stack). Alternately or additionally, the application window may besnapped into the region.

Concluding the example referencing workspace 400, window managerpresents application window 438 in a quadrant of workspace 400, whichplaces application window 438 against the other snapped windows ofworkspace 400. Additionally, in the context of workspace 402, windowmanager places application window 440 against half-snapped applicationwindow 414.

FIG. 5 depicts a method 500 for sizing and positioning an applicationwindow based on other application windows of a multi-applicationenvironment, including operations performed by windows manager 132 ormulti-application environment module 118. In portions of the followingdiscussion reference may be made to system 100 of FIG. 1, operatingenvironment 200 of FIG. 2, and other methods and example embodimentsdescribed elsewhere herein, reference to which is made for example only.

At 502, input is received to initiate placement of an application windowin a region of a multi-application environment. Placement of theapplication window may be responsive to input to add, switch, or move anapplication window in the multi-application environment. In some cases,the input is a gesture or edge trigger action in which an applicationwindow, or visual representation thereof, is dragged to or moved againstan edge of the multi-application environment. In such cases, theapplication window's contact or movement into the edge of themulti-application environment can ‘trigger’ a placement, or othertransformation, of the application window.

At 504, respective sizes and positions of other application windows inthe multi-application environment are determined. In some cases,respective edges of the other application windows are identified ascomplimentary or non-complimentary edges to the region. In such cases,these respective edges may be identified on a per-axis basis, such as avertical axis or horizontal axis. When complimentary edges of otherapplications are identified along both axes (e.g., two adjacentapplication windows), edges of the horizontal axis may be disregarded.

Optionally at 506, respective states of the other application windowsare determined. Application windows that are not snapped within amulti-application environment or are occluded by other windows may bedisregarded from other operations of method 500. Alternately oradditionally, application windows that are minimized, maximized, orpresented via another display may also be disregarded from the otheroperations of method 500. By so doing, currently snapped or primarywindows of the multi-application environment are considered when sizingor positioning the application window to provide an optimized layout ofapplication windows. In some cases, a data structure of informationdescribing the other application windows (e.g., on-screen applicationwindows) and their respective state information is created ormaintained. This data structure can be accessed or consulted todetermine which application windows to consider when optimizing a layoutof the application windows.

At 508, a size and position for the application window are determinedbased on the respective sizes and positions of the other applicationwindows. In some cases, the size and position of the window are alsodetermined based on properties or preferences of the application window,such as a default aspect ratio or minimum size. In other cases,properties or preferences of the other application windows may beconsidered, such as to maintain a minimum size of one of the otherapplication windows.

In some embodiments, the application window is sized and positioned toline up with other application windows that are adjacent to the regionin which the application window is selected for presentation. Forexample, the application window may be sized to line up with acomplimentary edge of an adjacent application window. When two of theother application windows are adjacent to the region, the applicationwindow may be sized to both complimentary edges of a vertically adjacentwindow. An example of this is illustrated in example workspace 600 ofFIG. 6, which includes application windows 602 and 604 that are adjacentto corner region 606. Here, a size and position are determined forapplication window 608 such that the application window aligns withapplication window 604.

Alternately, if another application window is not vertically adjacent,the application window can be sized to a horizontally adjacent window.This is illustrated by example workspace 610, which includes applicationwindow 612 that is horizontally adjacent to half-region 614. Here, asize and position are determined for application window 616 such thatthe application window aligns with a complimentary edge of applicationwindow 612.

Further, when an adjacent application window does not have acomplimentary edge in the region, the application window can be sizedand positioned to line up with a non-complimentary edge of the adjacentwindow. This is illustrated by example workspace 618, which includesapplication window 620 that is adjacent to corner 622. Here, a size andposition are determined for application window 624 to align theapplication window with a non-complimentary edge of application window620.

Additionally, when another application window is not adjacent to theregion, the application window can be sized to a complimentary edge of anon-adjacent region. This is illustrated by example workspace 626, whichincludes application window 628 that is not adjacent to corner 630.Here, a size and position are determined for application 632 to alignthe application window with a complimentary edges of application window628.

Alternately, when there are no other edges or application windowspresent, the application window can be sized and positioned to apredefined area of the multi-application environment, such as a quadrantarea or half area. This is illustrated in example workspaces 700 and 702of FIG. 7, which do not include an adjacent application window or thosehaving complimentary edges. In workspace 700, application window 704 issnapped to half the workspace and located opposite of corner 706. Assuch, a size and position are determined such that application window708 half snaps into an upper region of work space 700. In workspace 702,there are no other application windows when application window 710 ismoved into a half-region. Accordingly, a size and position aredetermined such that window 710 can be snapped into a half-snap area ofworkspace 708.

Optionally at 510, a respective size or position of one of the otherapplication windows is altered. In some cases, a size or position of theother application window is determined based on properties orpreferences of the other application window, such as a default aspectratio or minimum size. Altering the other application window may includemoving or sizing the other application window to fit or fill apredefined area of the multi-application environment, such as a quadrantarea or half area.

In some embodiments, this can be effective in enabling applicationwindow swapping, such as when the application window and anotherapplication window are similarly sized. Examples of this are illustratedin workspaces 712 and 714 of FIG. 7, in which application windowswapping is initiated in response to half-snap and quarter-snap edgetrigger actions (triggers), respectively. In workspace 712, half-snapedge trigger 716 is received via application window 718 to move theapplication window to the right edge of workspace 712.

Here, application windows 720 and 722 are repositioned to the left edgeof workspace 712 thereby enabling a position swap with applicationwindow 718. In workspace 714, quarter-snap edge trigger 724 is receivedvia application window 726 to move the application window to theupper-left corner of workspace 714. Here, application window 728 isrepositioned to the lower-left corner of workspace 714 thereby enablinga position swap with application window 726.

An example algorithm to determine when to initiate an application windowswap is based on the input moving one of the application windows. Whenedge components of the application windows that are perpendicular tomovement are identical, the application windows can be swapped. In otherwords, when moving an application window along the X-axis, theapplication window edges in the Y-axis must match. For diagonalmovement, this algorithm can be applied twice, once in each axialdirection. Vector-based movement along each axis may be determined bymapping the movement back to an edge trigger or other directional input.

At 512, the application window is presented at the determined size andposition to complete placement of the window. In some cases, theapplication window is presented over another application windowoccupying the selected regions. In such cases, the other applicationwindow may be relegated to another primacy layer of themulti-application environment (e.g., deeper in the z-stack). Alternatelyor additionally, the application window may be snapped into the regionat a predefined size, such as to occupy a quadrant-area or half-area ofthe multi-application environment.

Further, method 300 or 500 may be implemented to resize an existingsnapped window or maximized window. Resizing these windows may beinitiated using any suitable input, such a half-snap or quadrant-snapedge triggers. In some cases, these operations are enabled responsive toreceiving additional input, such as a mouse button or keyboard input(e.g., ALT key), in addition to an edge trigger or window dragginginput.

FIG. 8 illustrates examples of resizing snapped application windows,which are shown with reference to workspaces 800 and 802. Workspace 800includes application window 804 and application window 806, which isinitially maximized in the workspace. Here, half-snap edge trigger 808positions and sizes application window 810 to a half-area of workspace800. In response to this, window manager 132 resizes application window806 to another half-area of workspace 800.

As another example, consider workspace 802, which includes applicationwindow 810 and application window 812 occupying a half-area of workspace802. Here, quadrant-snap edge trigger 811 positions and sizesapplication window 810 to a quadrant-area of workspace 802. In responseto this, window manager 132 resizes application window 812 to anadjacent quadrant-area of workspace 802. These are but a few examples ofhow methods 300 and 500 can be implemented to position or size snappedapplication windows.

Region-Based Sizing and Positioning of Application Windows

FIG. 9 depicts a method 900 for region-based sizing of applicationwindows, including operations performed by windows manager 132 ormulti-application environment module 118. In portions of the followingdiscussion reference may be made to system 100 of FIG. 1, operatingenvironment 200 of FIG. 2, and other methods and example embodimentsdescribed elsewhere herein, reference to which is made for example only.

At 902, an application window is presented in a user interface havingpredefined areas. The application window may be presented in one of thepredefined areas or over the predefined areas. Each of the predefinedareas corresponds with a region of the user interface. In some cases,the regions (e.g., edges) of the user interface are used to triggerplacement of an application window into a corresponding one of thepredefined areas (e.g., quadrants). These regions of the user interfacemay be default regions, such as screen edges, or user-defined regionsthat include any section of the screen. In some cases, the predefinedareas may have an associated size or position within the user interface,such as a quadrant size, half size, maximized size, minimized size, andso on. The user interface may be implemented as a multi-applicationenvironment.

By way of example, consider FIG. 10, which illustrates examplepredefined areas and corresponding regions. By way of example only, thepredefined areas are illustrated as snap-areas, which may be evenly orunevenly split across sections of a workspace. For instance, workspace1000 of FIG. 10 includes half-snap area 1002 and half-snap area 1004,which correspond edge region 1006 and edge region 1008, respectively.

Example workspace 1010 includes quadrant areas, such as quadrant-snapareas 1012, 1014, 1016, and 1018, which correspond to corner regions1020, 1022, 1024, and 1026, respectively. Corner regions may be definedas square or round (e.g., corner region 1026), and may have a predefinedsize, such as a width or radius of approximately 25 pixels. Otherexample half areas are shown in workspace 1028, which includes half-snaparea 1030 and half-snap area 1032. Edge region 1034 may correspond witha maximized area of a workspace or, in the case of a portrait-orienteddisplay, may correspond with half-snap area 1030. Finally, half-snaparea 1032 corresponds with edge region 1036 located along the bottom ofworkspace 1028.

In some embodiments, a size of a region may be altered depending on atype of input expected. For example, when a more-precise input isreceived, such as mouse input, regions may have a smaller size because auser can easily engage an intended region. In other cases, the size ofthe regions (e.g., edge region or corner edge) may be increased whenless-precise input is received, such as touch input or gesture input.Alternately or additionally, a size of a region may be altered based ondisplay topology, such as providing larger regions where edges ofdisplays meet to enable more-accurate region selection.

At 904, a size of the application window is altered based on one of thepredefined areas. The size of the application window is altered inresponse to input moving the application window into a region thatcorresponds with the predefined area. In some cases, the applicationwindow is positioned to occupy a portion or all of the predefined area.The input moving the application window may include any suitable input,such as an edge trigger or directional input (e.g., dragging) receivedthrough the application window. For example, dragging an applicationwindow into a corner region sizes the application window into a quadrantthat corresponds to the corner region. Thus, an application window canbe sized to any predefined area of a workspace by moving that window toa corresponding region.

FIG. 11 depicts a method 1100 for region-based sizing and positioning ofapplication windows, including operations performed by windows manager132 or multi-application environment module 118. In portions of thefollowing discussion reference may be made to system 100 of FIG. 1,operating environment 200 of FIG. 2, and other methods and exampleembodiments described elsewhere herein, reference to which is made forexample only.

At 1102, input is received to move an application window within a userinterface having predefined areas. The input received may include anysuitable type of input, such as key strokes, directional input, gestureinput, and the like. For example, the input may include selection anddragging of the application via a mouse or one or more key strokes, suchas the Windows™ key and an arrow key. In other instances, theapplication may be dragged into a region that corresponds with one ofthe predefined areas.

At 1104, a predefined area of the user interface is selected based onthe input and the state of the application window. The state of theapplication window may include a current size, a current position, acurrent depth in the z-stack, or a current predefined area occupied bythe application window. The predefined area may include any predefinedarea, such as a user defined area or other predefined area describedherein, such as snap areas. In some embodiments, the predefined areasmay also be overlapping and have customizable depths in the z-stack ofwindows. By so doing, application window layouts of varying primacy ordepth can be created.

Using the state of the application window can enable dynamic sizing andpositioning of the application window. By way of example, selection of apredefined area or application window state can be determined using astate machine. In some cases, accessing the state machine based on acurrent state of an application window and the input received can selecta next-predefined area or next-state for the application window.

Consider FIG. 12, which illustrates example state machine 1200 fordynamically selecting predefined areas or states for applicationwindows. Here, legend 1202 indicates which state transitions occur inresponse to a respective input received, such as an arrow key pressedwhile holding a Windows™ key. As shown by states of state machine 1200,predefined areas can be selected by entering a series of keystrokes toreach a corresponding state. In this particular example, state machine1200 includes states for half areas, such as left half 1204, right half1206, split top 1208, and split bottom 1210. State machine also includesstates for quadrant areas, such as left-top quarter 1212, left-bottomquarter 1214, right-top quarter 1216, and right-bottom quarter 1218.Further, other predefined areas or states of state machine 1200 are alsoselectable and include minimize 1220, restore 1222, and maximize 1224.Alternately or additionally, a user can map one or more of the states,or other key combinations, to custom user-defined areas of a workspace.

Returning to the method at hand, at 1106, a size and position of theapplication window are altered such that the application window willfill the predefined area. In some cases, the application window is sizedto fill a quadrant area or half area of the user interface. In othercases, the application window may be minimized or relegated deeper in az-stack of currently presented application windows. As noted above, thepredefined area may be user defined, such as a drop region in a centerof a user interface or multi-application environment.

By way of example, consider workspace 1300 of FIG. 13, which illustratescustom drop areas 1302, 1304, and 1306. These custom drop areas may bedefined by a user and mapped to a region (e.g., a region in the middleof the workspace) or key combination such that a size and position of anapplication window are altered to fill the drop area. These drop areasmay be configured in any suitable fashion, such as by storing anapplication window's size, position, or depth in a z-stack as auser-defined area of a workspace.

Optionally at 1108, the application window is previewed to visiblyindicate the altered size and position of the application window. Thepreview of the application window can be shown as a non-opaque (orpartially transparent) representation of the application window orcontent thereof. In some cases, additional input is received confirmingthe previewed placement of the application window in the predefinedarea. In such cases, method 500 may advance to operation 1110 inresponse to input committing the application window as previewed.

Alternately, the additional input may select another of the predefinedareas in which to present the application interface. This may beeffective to cause method 500 to return to operation 1102 for selectionof another predefined area. In yet other cases, the additional input maybe received in the form of continued dragging or inertia imparted on theapplication window or the preview thereof. In response to this continueddragging or inertia (e.g., into an edge region), the preview of theapplication window can be resized in the predefined area or sized toanother predefined area.

At 1110, the application window is presented in the predefined area ofthe user interface at the altered size and position. In some cases, theapplication window is presented at a particular depth in the z-stack inaccordance with a depth associated with the predefined region of theuser interface. Presenting the application at the altered size andposition can be effective to fill the predefined area. An example ofthis is illustrated by workspace 1308 in which search application 1310is sized and positioned to fill drop areas 1302. In the context of FIG.13, operations of method 1100 may be repeated to fill drop areas 1304and 1306 with image application 1312 and notepad application 1314,respectively.

Dynamic Joint Dividers for Application Windows

FIG. 14 depicts a method 1400 for establishing a joint divider betweenapplication windows, including operations performed by windows manager132 or multi-application environment module 118. In portions of thefollowing discussion reference may be made to system 100 of FIG. 1,operating environment 200 of FIG. 2, and other methods and exampleembodiments described elsewhere herein, reference to which is made forexample only.

At 1402, a joint divider is established between a first applicationwindow and a second application window of a multi-applicationenvironment. The joint divider is established in response to an edge ofthe first application window contacting (e.g., touching with no overlap)an edge of the second application window. In some cases, the jointdivider is established along respective sections of each applicationwindow that are in contact. In other cases, the joint divider isestablished along an entire length of each respective applicationwindow, regardless of an amount of contact between the applicationwindows. Contact between the edges of the application windows may becaused by any suitable operation, such as moving, snapping, adding, orsizing one of the application windows in the multi-applicationenvironment. The joint divider can also be established along any visibleedges of the application windows. In some cases, establishing the jointdivider may be limited to snapped application windows and precludenon-snapped or floating application windows.

In some embodiments, the joint divider is established between multipleapplication windows contacting each other along one or more edges. Forexample, a single joint divider can be established when respective edgesof two applications windows contact an edge of a third applicationwindow. Alternately, complex joint dividers can be formed whenapplication windows contact each other at respective corners of theapplication windows. Alternately or additionally, establishing the jointdivider groups (or relates) the application windows together enablingoperations to be performed on the grouped application windows. Forexample, grouped application windows may be opened, closed, minimized,resized, switched to/from, or moved together. Further, ungrouping thegrouped application windows may return the previously-groupedapplication windows to their respective original states. In some cases,the grouped application windows are presented together in switchingaffordances, such as a start menu, application management UI, or hotkeyswitcher (e.g., ALT+Tab or Windows™+Tab).

A joint divider can be established whenever and wherever respectiveedges of two or more application windows contact each other. By way ofexample, consider FIG. 15 which illustrates various joint dividers inworkspaces 1500, 1502, and 1504. Workspace 1500 includes joint divider1506 established between quadrant-snapped application windows and jointdivider 1508 established between the quadrant-snapped applicationwindows and a half-snapped application window. Joint dividers may alsobe established between occluded application windows as shown inworkspace 1502 where application divider 1510 is established betweenpartially-occluded and snapped application windows. Further, applicationdivider 1512 is established between occluded and floating applicationwindows, which are not at a highest level in the z-stack of applicationwindows.

At 1404, the joint divider shared by a first application window and asecond application window is presented. Presenting the joint divider mayinclude providing a visual or haptic indication of the joint divider.For example, a visual indication is presented over edges of applicationwindows that share the joint divider. In other cases, the joint divideris presented between two application windows that share the jointdivider. In such cases, the size of one or both application windows maybe reduced to provide space in which to present the joint divider.Alternately or additionally, haptic feedback (e.g., bumps orundulations) can be used to indicate a presence of the joint divider. Insome cases, the joint divider is presented in response to input orcursor movement that is proximate the joint divider.

In some embodiments, a joint-separation control or affordance is alsopresented to enable a joint divider to be disabled. The joint-separationcontrol can be presented over a section of the joint divider, an edge ofthe joint control, or both edges of the joint control. In some cases,the joint-separation control enables a user to ‘unbuckle’ the jointdivider, which enables individual sizing or movement of applicationwindows previously sharing the joint divider. The joint divider may alsobe disabled by other operations, such as double-clicking the jointdivider, clicking the joint divider while holding a key (e.g., CTRL), orby sizing or moving an application window via an edge that is not partof the joint divider.

The joint divider can be presented in response to establishing the jointdivider between application windows. Alternately, the joint divider mayexist without being presented until input or cursor movement is receivedproximate to the joint divider. FIG. 16 illustrates an example ofpresenting a joint divider in response to cursor movement. Movement of acursor is shown in a progression of illustrated workspaces starting inworkspace 1600, which includes application window 1602, applicationwindow 1604, and cursor 1606.

As shown in workspace 1608, movement of cursor 1606 can be detectedbased on proximity threshold 1610. Proximity threshold 1610 may beconfigured having any suitable dimensions, such as 10 pixels from ajoint divider, and may be reconfigured based on a type of input beingreceived. As cursor 1606 crosses proximity threshold 1610, as shown inworkspace 1612, joint divider 1614 and joint-separation control 1616 arepresented over contacting edges of application windows 1602 and 1604.

At 1406, input to alter respective sizes of the first application windowand the second application window is received via the joint divider. Theinput received may include any suitable type of input, such asdirectional input received via a cursor movement, touch input, or arrowkeys. By way of example, consider example workspace 1700 of FIG. 17,which includes joint divider 1702 shared by application windows 1704 and1706. In this particular example, joint divider 1702 also includesjoint-separation control to enable individual sizing of applicationwindows 1704 and 1706. Here, input to size application windows 1704 and1706 in a lateral direction is received via cursor 1710.

At 1408, the respective sizes of the first application window and thesecond application window are altered simultaneously in response to theinput. The respective sizes of the application windows may be altered asthe input, such as directional cursor movement, is received. Forexample, the altered sizes of the application windows may be visuallyindicated by sliding the joint divider along an axis in which input isreceived. Thus, the sliding joint divider may visually indicate thesimultaneous sizing of the first and second application windows.

Alternately or additionally, joint dividers may exhibit an attraction oraffinity (e.g., magnetism) for midpoints along an edge of a workspace.This can be effective to aid a user in sizing windows in a symmetricallayout. In some cases, the attraction to points along edges of theworkspace can be disable in response to key input (e.g., holding theCTRL key).

In the context of FIG. 17, application windows 1704 and 1706 are sizedbased on the movement of joint divider 1702 to a position shown inworkspace 1712. In this particular example, features of thejoint-separation control are also illustrated. Here, additional input toindependently size application window 1704 is received viajoint-separation control 1708. As shown, input received from cursor 1710sizes application window 1704 an opposite lateral direction. As aresult, application window 1704 is separated from application window1706 as shown in workspace 1714, disabling the joint divider, and sizedto expose previously-occluded application windows 1716.

FIG. 18 depicts a method 1800 for sizing and positioning applicationwindows with a joint divider, including operations performed by windowsmanager 132 or multi-application environment module 118. In portions ofthe following discussion reference may be made to system 100 of FIG. 1,operating environment 200 of FIG. 2, and other methods and exampleembodiments described elsewhere herein, reference to which is made forexample only.

At 1802, a joint divider shared between a first application window and asecond application window is presented in a multi-applicationenvironment. Presenting the joint divider may include providing a visualor haptic indication of the joint divider. For example, a visualindication is presented in between or over edges of application windowsthat share the joint divider. Alternately or additionally, hapticfeedback (e.g., bumps or undulations) can be used to indicate a presenceof the joint divider. By way of example, consider workspace 1900 of FIG.19 in which application window 1902 and application window 1904 sharejoint divider 1906. Here, joint divider 1906 is visually indicated overcontacting edges of application window 1902 and application window 1904.

At 1804, input to increase a size of the first application window isreceived via the joint divider. In some cases, the input to increase thesize of the first application window may indicate to increase the sizeof the first application window in a direction toward the secondapplication window. In such cases, depending on a position of the secondwindow with respect to an edge of a workspace, the input may indicate tosize, move, or relegate the second application deeper into a z-stack ofwindows. For example, application windows not touching an edge of amulti-application environment may be moved rather than sized.

The input received may include any suitable type of input, such asdirectional input received via a cursor movement, touch input, or arrowkeys. In the context of the current example, directional input isreceived via application divider as shown in workspace 1900 of FIG. 19.Here, note that application window 1904 is not in contact with an edgeof workspace 1900 and is thus movable without being sized.

At 1806, the size of the first application window is increased inresponse to the input received. While the size of the first applicationwindow is increased the second application window is simultaneouslymoved effective to maintain a size of the second application window.Movement of the second application window may continue until an edge ofthe multi-application environment is encountered. Continuing the ongoingexample, a size of application window 1902 is increased whileapplication window 1904 is moved toward an edge of workspace 1908.

Operations 1808, 1810, and 1812 are optional and may be performedresponsive to additional input or further increases in the size of thefirst application window. At 1808, a size of the second applicationwindow is decreased in response to an edge of the second applicationwindow encountering an edge of the multi-application environment.Decreasing the size of the second application window occurs while thesize of the first application window continues to increase. The size ofthe second application window may be decreased until a minimum windowsize is reached. In the context of FIG. 19, this is illustrated in layerview 1908 where continued movement of joint divider 1906 increase thesize of application window 1902 and decreases a size of applicationwindow 1904.

At 1810, the first application window is permitted to overlap the secondapplication window in response to the size of the second applicationwindow reaching a minimum size. Once the minimum size of the secondapplication window is reached, the advancing edge of the firstapplication begins to overlap the second application window. The minimumsize of the application window may be defined by an applicationassociated with the application user interface, an operating system, orby user input. Continuing the ongoing example, a minimum size ofapplication window 1904 is reached by joint divider 1906 as shown inlayer view 1910. In response to this and as illustrated in layer view1912, an advancing edge of application window 1902 begins to overlapapplication window 1904.

At 1812, the second application window is relegated to another layer ofthe multi-application environment in response to the joint dividerencountering the edge of the multi-application environment. In somecases, the second application window is pushed deeper into a z-stack ofapplication windows. Alternately or additionally, the size of the secondapplication window can be restored to a default size or a size previousto being moved. This can be effective to enable the second applicationwindow to be restored or switched to without resizing. Concluding thepresent example, application window 1904 is relegated to a next-layer ofthe workspace at a restored size. Thus, application window 1904 can berestored or switched to without resizing.

Joint dividers may also be established between multiple applicationwindows and may be referred to as complex joint dividers. Sizing ormovement of multiple application windows may be implemented by operationdescribed with respect to method 1400 or 1800. By way of exampleconsider FIG. 20, which includes example workspaces 2000 and 2002illustrating joint dividers established between multiple applicationwindows. In the context of workspace 2000, joint divider 2004 enablessizing of application windows 2006 and 2008, which are adjacent to eachother and share joint divider 2004. Joint divider 2010, which is sharedbetween edges of application windows 2006, 2008, and 2012 enables sizingof all three application windows.

This aspect can be extended to four application windows as shown inworkspace 2002, which includes application windows 2014, 2016, 2018, and2020. In this example, joint dividers 2022, 2024, 2026, and 2028 eachenable sizing of their respective adjacent windows that share edges. Forexample, joint divider 2022 sizes application windows 2014 and 2016, butnot application windows 2018 or 2020. Alternately or additionally, whensizing multiple windows, a joint divider may separate or ‘unbuckle’ inresponse to sizing one of the multiple windows to a minimum size.

Complex joint dividers may also be implemented to maintain anindependence of a window or localize changes to a particular windows.For example, consider workspaces 2030, 2032, and 2034 of FIG. 20, whichillustrate a three floating application windows that share a jointdivider. Here, application windows 2036, 2038, and 2040 share jointdivider 2042. As shown in workspace 2030, input 2044 received via asection of joint divider 2042 shared by application windows 2036 and2040 sizes those application windows but not application window 2038.Another example of this independent sizing is shown in workspaces 2032,in which input 2046 sizes application window 2040 over applicationwindows 2036 and 2038. Alternately, input 2048 received via a section ofjoint divider shared by application windows 2038 and 2040 can size theseapplication windows as shown in workspace 2034.

Joint dividers may also be implemented in combination to provide jointcorners. Joint corners enable application window sizing in one or twoaxes and may size at least two application windows that share the jointcorner. FIG. 20 illustrates various examples of corner joints as shownin workspaces 2100 and 2102. In workspace 2100, corner joint 2104enables application windows 2106, 2108, 2110, and 2112 to be sized inboth axes.

In some cases, joint corners can be established when two applicationwindows share a corner and not a common edge. An example of this isillustrated by workspace 2102 in which application windows 2114 and 2116meet at corners and share joint corner 2118. Here, joint corner 2118enables sizing of application windows 2114 and 2116 in both axes. Aswith joint dividers, joint corners may be disabled responsive toreaching an application windows minimum size or other suitable input,such as key input or dragging an application window from an edge that isnot part of the joint corner.

Joint corners can be established whenever corners of application windowscontact or touch each other. Window manager 132 can establish ormaintain joint corners by tracking corner, or two adjacent edges, ofindividual windows. Returning to FIG. 21, consider example workspace2120 that includes application windows 2122, 2124, and 2126. Each ofthese windows includes a corner where two of their respective edgesmeet. Here, window manager 132 tracks edges 2128, 2130, and 2132 toestablish or maintain a joint corner for these application windows.

Window manager 132 may also track edges of individual applicationwindows to establish or maintain joint dividers. By way of example,consider FIG. 22 in which workspace 2200 includes application windows2202 and 2204. Application windows 2202 and 2204 share joint divider2206, and thus can be sized through input received through the jointdivider. To enable sizing or other joint divider operations windowmanager 132 can build a dependency chain to track individual edges ofapplication windows.

In the context of FIG. 22 and as shown in detailed view 2208, jointdivider 2206 includes edge 2210 of application window 2202 and edge 2212of application window 2204. Here, cursor 2214 is hovering over edge 2212of application window 2204 and window manager 132 can build a dependencychain with respect to edge 2212 and a position of cursor 2214. Startingfrom edge 2212, window manager determines which other application windowedges are in contact with edge 2212. Here, edge 2210 is determined to becontacting edge 2212 as shown in detailed view 2216, and is thusaffected by joint divider 2206.

Alternately or additionally, non-contiguous edges may be disregarded andignored when performing joint divider operations. For example, indetailed view 2218, window manager 132 determines that edges ofapplication windows 2220 and 2222 are in contact with edge 2212. An edgeof application window 2224, however, is determined to not be in contactwith edge 2212 because of intervening application window 2226 and may bedisregarded. As shown in detailed view 2228, Application window 2226 mayalso be determined as not contacting edge 2212 and may also bedisregarded for joint divider operations.

FIG. 23 further illustrates an example of edge dependency at detailedview 2300, in which edge 2302 of application window 2304 is determinedto be in contact with edge 2306 of application window 2308. Fromapplication window 2304, window manager 132 can determine contact fromthe perspective of a next application window in an edge dependencychain. Here, edge 2310 of application window 2312 is determined to be incontact with edge 2306 of application window 2308. In detailed view2314, a size operation initiated by input 2316 is propagated through thedependency chain and causing each of the contacting application windowsto size or move accordingly.

Assisted Presentation of Application Windows

FIG. 24 depicts a method 2400 for presenting selectable applicationwindows in an available region of a multi-application environment,including operations performed by windows manager 132 ormulti-application environment module 118. In portions of the followingdiscussion reference may be made to system 100 of FIG. 1, operatingenvironment 200 of FIG. 2, and other methods and example embodimentsdescribed elsewhere herein, reference to which is made for example only.

At 2402, visual representations of application windows are presented inan available region of a multi-application environment. The visualrepresentations correspond to application windows that are selectable orsuitable for presentation in the available area, such as applicationwindows that can be sized to fully-occupy the available region. Thevisual representations of the application windows may include text,icons, or reduced-sized images of the application windows, such asthumbnail images. These reduced-sized images may visibly indicate apreview of an application windows content or previously-presentedcontent.

In some embodiments, the visual representations of the applicationwindows are presented via a prompt or other application-selectioninterface in the available region. In some cases, the visualrepresentations are presented in response to presenting anotherapplication in another region of the multi-application environment, suchas a snap operation to present the other application in a quadrant-areaor half-area. In other cases, the visual representations are presentedin response to input received via an application-selection control, suchas a control to invoke the prompt or application-selection interface.The application-selection control may be implemented as a hover-regionor graphical tab near along an edge of the available area.

An application-selection control may also be presented in response tocursor movement or other input that ‘pushes’ into an edge region of themulti-application environment. The push movement may include a doublepush movement or movement over a distance of workspace or screen area.In some cases, a push movement is detected using particular criteria toavoid recognizing inadvertent contact with an edge (e.g., scrolling ascrollbar) as push movement. For example, once movement of a cursorpauses at, or just within, an edge region, a subsequent ‘push’ (e.g.,double push) further into the edge region can invoke theapplication-selection control. Alternately, the application-selectioncontrol may not be invoked if the cursor leaves the edge region, alength of the pause fails to meet a predefined threshold, or the cursorcontinues to move through the edge region without pausing.

In some embodiments, movement of a cursor prior to encountering an edgeregion can also be considered. Vertical and horizontal components ofcursor movement may be tracked to determine if the cursor travelled farenough across a workspace or into the edge region at a sufficient angle.By way of example, when encountering a horizontal edge, theapplication-selection control can be invoked in response to determiningthat the cursor travelled at least 150 vertical pixels and moved morevertically than horizontally within the edge region. Similar criteriamay be applied to vertical edge regions, such as by determining that thecursor moved more horizontally than vertically within the edge region.Alternately or additionally, cursor movement or other input can betracked by a state machine configured to invoke or trigger presentationof the application-selection control in response to these criteria beingmet.

By way of example, consider FIG. 25 in which example workspace 2500 of amulti-application environment is illustrated. Workspace 2500 includesapplication window 2502, available region 2504, and taskbar 2506. Inthis particular example, application-selection prompt 2508 is presentedin available region 2504, which also includes application-selectioncontrol 2510. A more detailed view of application-selection control 2510is provided at 2512 and includes dismiss control 2514.

Application-selection control 2510 is implemented as a hover regionalong an edge of available region 2504 and appears responsive toproximity to cursor 2516 (or touch input). The hover region may have apredefined width or area, such as 10 to 25 pixels along an edge of aworkspace. Application-selection control 2510 enables a user to triggeror invoke application selection-prompt 2508, which may then present allactive application windows to the user in a contextual fashion.Alternately or additionally, dismiss control 2415 enablesapplication-selection prompt 2508 to be dismissed (or hidden)temporarily or until subsequent proximity with a cursor or other input.Here, assume that a user has tapped application-selection control 2510to invoke application-selection prompt 2508. In response to this input,application-selection prompt 2508 is presented and includes visualrepresentations (e.g., thumbnail images) of application windows thatwere most-recently accessed by the user.

Alternately or additionally, the visual representation of theapplication windows may be presented in response to presenting anotherapplication window in another region of the multi-applicationenvironment. This may be effective to enable a user to easily select oneof the application windows for the available region to complete a layoutof application windows in the multi-application environment.

An example of this is shown in workspace 2518 of FIG. 25, in which edgetrigger 2520 is received via application window 2522. Edge trigger 2520half-snaps application window 2522 to an edge of workspace 2518 andapplication window 2522 is presented in the half-snap region. Thisexample illustrates but one instance in which an edge trigger or othercontact with an edge can be effective to cause presentation or‘snapping’ of an application window into a predefined area thatcorresponds with the edge. Here, note that unsnapped (e.g., floating)application windows 2524 are partially-occluded before the half-snapoperation of application window 2522. In response to the presentation ofapplication window 2522 in the half-snap region, visual representations2528 that correspond to unsnapped application windows 2524 are presentedin application-selection prompt 2528.

At 2404, one of the application windows is presented in the availableregion. The application window is presented in response to receivinginput selecting a corresponding one of the visual representations. Insome cases, the input selecting the visual representation is receivedvia other application-selection user interfaces, such as an applicationmanagement UI, start menu, or key-based application switcher (e.g.,ALT+Tab keys).

The application window is sized and positioned to fill or completelyoccupy the available region. Prior to presenting the application window,a preview of the application window may be presented to visibly indicatethe size and position of the application window within the availableregion. In the context of FIG. 25 and workspace 2500, the user tappingemail application tile 2530 would cause a corresponding emailapplication to fill available region 2504. Thus, with a single tapinput, the user is able to conveniently optimize a layout of theworkspace.

FIG. 26 depicts a method 2600 for identifying an available region of amulti-application environment in which to present an application window,including operations performed by windows manager 132 ormulti-application environment module 118. In portions of the followingdiscussion reference may be made to system 100 of FIG. 1, operatingenvironment 200 of FIG. 2, and other methods and example embodimentsdescribed elsewhere herein, reference to which is made for example only.

At 2602, an available region of a multi-application environment isidentified. The available region may include any suitable region inwhich an application interface can be presented, such as a rectangularregion of workspace or screen. Identification of the available regionmay be performed in response to presentation of another applicationwindow in another region of the multi-application environment. The otherapplication window may be presented in the other region via any suitableoperation, such as a snap operation, sizing via a dynamic joint divider,or region-based sizing. In some cases, the available region isidentified as a region that does not include an un-occluded window or aregion that can be fully occupied by an application window. Alternatelyor additionally, the available region is identified for a primary orforemost one layer of the multi-application environment (e.g., top ofthe z-stack).

Consider FIG. 27 in which workspace 2700 is presented generally at 2702and includes application windows 2702, 2704, 2706, and 2708, the latterthree being partially occluded by application window 2702. Here, assumethat half-snap edge trigger 2710 is received via application window2702, which is then snapped to the right half of workspace 2700 as shownat 2712. In response to this snap operation, window manager 132identifies the left half of workspace 2700 as available area 2714.

Optionally at 2604, application windows that are selectable forpresentation in the available region are determined. These applicationwindows may include any suitable application window, such as applicationwindows that are occluded, partially-occluded, minimized, or groupedwith another active or open application window. Candidate applicationwindows for selection may also sizable to fill the available region, sofixed-size application windows and application windows snapped to otherregions can be excluded.

At, 2606 visual representations of application windows are presented inthe available region. These application windows include thoseapplication windows that are selectable for presentation in theavailable region. The visual representations of the application windowsmay include text, icons, or reduced-sized images of the applicationwindows, such as thumbnail images. These reduced-sized images mayvisibly indicate a preview of an application windows content orpreviously-presented content. In the context of the present example andas shown at 2712, window manager 132 presents visual representations,such as reduced-size images, of application windows 2704, 2706, and 2708in available region 2714 of workspace 2700.

Alternately or additionally, an order or layout for the visualrepresentations of the application windows is determined. This order orlayout may be determined based any characteristic or property of theapplication windows, such as most-frequent-use, most-recent-use, names,titles, sizes, position in the z-stack, or grouping with another activeor open application window.

At 2608, input selecting one of the application windows is received viaa corresponding one of the visual representations. The input may includeany suitable input, such as cursor input, gesture input, or touch input.In some cases, the touch input includes a tap or quadrant-snap orhalf-snap into the available region. Continuing the ongoing example,quadrant-snap trigger 2716 is received via the visual representation ofapplication window 2706.

At 2610, the selected application window is presented in at least aportion of the available region. The application window is sized andpositioned to fill or completely occupy the available region. Prior topresenting the application window, a preview of the application windowmay be presented to visibly indicate the size and position of theapplication window within the available region. Optionally, operationsof method 2600 may be performed repeatedly to fill other availableregions of the multi-application environment. By so doing, an optimizedlayout of application windows can be provided with minimal userinteraction.

In some embodiments, an application window may be selected for the userand presented in the available region without user input. For example,if an application window is paired with another application window inanother region, the paired application window can be presented inresponse to presentation other application window in the other region.The application window may also be selected automatically based oncriteria used to determine which applications are selectable forpresentation, such as a most-recently user or most-frequently usedapplication window.

Concluding the present example, window manager 132 sizes and positionsapplication window 2706 to fill a quadrant of workspace 2700 as shown at2718. Further, window manager 132 may then identify available region2720 of workspace 2700 in which to present the visual representations ofapplication windows 2704 and 2708. Here, assume that tap input 2722 isreceived via the visual representation of application window 2708. Inresponse, window manager 132 sizes and positions application window 2708to fill a quadrant region of workspace 2700 as shown at 2724. Thus, withjust three instances of input, a layout of application windows have beenprovided in workspace 2700.

Aspects of these methods may be implemented in hardware (e.g., fixedlogic circuitry), firmware, a System-on-Chip (SoC), software, manualprocessing, or any combination thereof. A software implementationrepresents program code that performs specified tasks when executed by acomputer processor, such as software, applications, routines, programs,objects, components, data structures, procedures, modules, functions,and the like. The program code can be stored in one or morecomputer-readable memory devices, both local and/or remote to a computerprocessor. The methods may also be practiced in a distributed computingenvironment by multiple computing devices.

Example Device

FIG. 28 illustrates various components of example device 2800 that canbe implemented as any type of client, server, and/or computing device asdescribed with reference to the previous FIGS. 1-28 to implementtechniques enabling dynamic joint dividers for application windows. Inembodiments, device 2800 can be implemented as one or a combination of awired and/or wireless device, as a form of television client device(e.g., television set-top box, digital video recorder (DVR), etc.),consumer device, computer device, server device, portable computerdevice, user device, communication device, video processing and/orrendering device, appliance device, gaming device, electronic device,and/or as another type of device. Device 2800 may also be associatedwith a user (e.g., a person) and/or an entity that operates the devicesuch that a device describes logical devices that include users,software, firmware, and/or a combination of devices.

Device 2800 includes communication devices 2802 that enable wired and/orwireless communication of device data 2804 (e.g., received data, datathat is being received, data scheduled for broadcast, data packets ofthe data, etc.). Device data 2804 or other device content can includeconfiguration settings of the device, media content stored on thedevice, and/or information associated with a user of the device. Mediacontent stored on device 2800 can include any type of audio, video,and/or image data. Device 2800 includes one or more data inputs 2806 viawhich any type of data, media content, and/or inputs can be received,such as user-selectable inputs, messages, music, television mediacontent, recorded video content, and any other type of audio, video,and/or image data received from any content and/or data source.

Device 2800 also includes communication interfaces 2808, which can beimplemented as any one or more of a serial and/or parallel interface, awireless interface, any type of network interface, a modem, and as anyother type of communication interface. Communication interfaces 2808provide a connection and/or communication links between device 2800 anda communication network by which other electronic, computing, andcommunication devices communicate data with device 2800.

Device 2800 includes one or more processors 2810 (e.g., any ofmicroprocessors, controllers, and the like), which process variouscomputer-executable instructions to control the operation of device 2800and to enable techniques enabling a multi-application environment.Alternatively or in addition, device 2800 can be implemented with anyone or combination of hardware, firmware, or fixed logic circuitry thatis implemented in connection with processing and control circuits whichare generally identified at 2812. Although not shown, device 2800 caninclude a system bus or data transfer system that couples the variouscomponents within the device. A system bus can include any one orcombination of different bus structures, such as a memory bus or memorycontroller, a peripheral bus, a universal serial bus, and/or a processoror local bus that utilizes any of a variety of bus architectures.

Device 2800 also includes computer-readable storage media 2814, such asone or more memory devices that enable persistent and/or non-transitorydata storage (i.e., in contrast to mere signal transmission), examplesof which include random access memory (RAM), non-volatile memory (e.g.,any one or more of a read-only memory (ROM), flash memory, EPROM,EEPROM, etc.), and a disk storage device. A disk storage device may beimplemented as any type of magnetic or optical storage device, such as ahard disk drive, a recordable and/or rewriteable compact disc (CD), anytype of a digital versatile disc (DVD), and the like. Device 2800 canalso include a mass storage media device 2816.

Computer-readable storage media 2814 provides data storage mechanisms tostore device data 2804, as well as various device applications 2818 andany other types of information and/or data related to operationalaspects of device 2800. For example, an operating system 2820 can bemaintained as a computer application with the computer-readable storagemedia 2814 and executed on processors 2810. Device applications 2818 mayinclude a device manager, such as any form of a control application,software application, signal-processing and control module, code that isnative to a particular device, a hardware abstraction layer for aparticular device, and so on.

Device applications 2818 also include any system components or modulesto implement the techniques, such as device applications 2818 includingmulti-application environment module 118, system-interface module 120,input module 122, application(s) 124, application manager 128, andwindow manager 132.

CONCLUSION

Although embodiments of techniques and apparatuses enabling dynamicjoint dividers for application windows have been described in languagespecific to features and/or methods, it is to be understood that thesubject of the appended claims is not necessarily limited to thespecific features or methods described. Rather, the specific featuresand methods are disclosed as example implementations enabling dynamicjoint dividers for application windows.

What is claimed is:
 1. A computer-implemented method comprising:presenting a first application window and a second application window ina multi-application environment; establishing, responsive to a firstedge of the first application window contacting a second edge of thesecond application window, a joint divider between the first and secondapplication windows; and altering respective sizes of the firstapplication window and the second application window simultaneously inresponse to input received via the joint divider.
 2. Thecomputer-implemented method as described in claim 1, further comprisingpresenting a visual indication of the joint divider.
 3. Thecomputer-implemented method as described in claim 2, wherein the visualindication of the joint divider is presented over respective portions ofthe first edge and the second edge that are in contact or presented inbetween the first and second windows.
 4. The computer-implemented methodas described in claim 1, further comprising: presenting a thirdapplication window in the multi-application environment; extending,responsive to a third edge of the third application window contactingthe second edge of the second application window, the joint dividerbetween the third and second application windows; and alteringrespective sizes of the first application window, the second applicationwindow, and the third application window simultaneously in response toinput received via the joint divider.
 5. The computer-implemented methodas described in claim 1, further comprising: presenting a thirdapplication window and a fourth application window in themulti-application environment; establishing, responsive to a third edgeof the third application window contacting a fourth edge of the fourthapplication window, another joint divider between the third and fourthapplication windows, the joint divider contacting the other jointdivider at a corner of one of the application windows; and alteringrespective sizes of the first application window, the second applicationwindow, the third application window, and fourth application windowsimultaneously in response to input received via the joint divider. 6.The computer-implemented method as described in claim 1, furthercomprising presenting a joint-separation control configured to enableindependent sizing of the first application window or the secondapplication window.
 7. The computer-implemented method as described inclaim 1, further comprising and prior to establishing the joint divider:moving the first or the second application window in themulti-application environment; adding the first or the secondapplication window to the multi-application environment; or sizing thefirst or the second application window to a region of themulti-application environment, the act of moving, adding, or sizingeffective to cause the contact between the first edge and the secondedge.
 8. A system comprising: one or more processors; one or morecomputer-readable media storing processor-executable instructions that,responsive to execution by the one or more processors, cause the one ormore processors to perform operations comprising: presenting a jointdivider shared by a first application window and a second applicationwindow in a multi-application environment; receiving, via the jointdivider, input to alter a size of the first application window or a sizeof the second application window; and altering the respective sizes ofthe first application window and the second application windowsimultaneously in response to the input received via the joint divider.9. The system as described in claim 8, wherein the operations furthercomprise indicating a presence of the joint divider in response toreceiving cursor input or touch input proximate the joint divider. 10.The system as described in claim 9, wherein the operations furthercomprise indicating the presence of the joint divider via hapticfeedback or a visual indication.
 11. The system as described in claim 8,wherein the operations further comprise presenting a joint-separationcontrol configured to enable independent sizing of the first applicationwindow or the second application window.
 12. The system as described inclaim 11, wherein the operations further comprise reducing respectivesizes of the first and second application windows to create spacebetween the first and second application windows, and wherein the jointdivider is presented in the space between the first and secondapplication windows and the joint-separation control is presented overthe joint divider.
 13. The system as described in claim 8, wherein theoperations further comprise disabling the joint control divider inresponse to independent movement of the first application window or thesecond application window, the independent movement initiated via arespective edge of the first application window or the secondapplication window that is not associated with the joint divider. 14.The system as described in claim 8, further comprising disabling thejoint control divider in response to additional input received via a keystroke or mouse button.
 15. One or more computer-readable media storingprocessor-executable instructions that, responsive to execution by oneor more processors, cause the one or more processors to performoperations comprising: presenting a joint divider shared by a firstapplication window and a second application window in amulti-application environment; receiving, via the joint divider, inputto increase a size of the first application window in a direction towardthe second application window; and increasing, responsive to the inputreceived, the size of the first application while concurrently movingthe second application window effective to maintain a size of the secondapplication window.
 16. The one or more computer-readable media asdescribed in claim 15, wherein the size of the first application isincreased until an edge of the second application window opposite of thefirst application encounters an edge of the multi-applicationenvironment and the operations further comprise decreasing, responsiveto the edge of the second application encountering the edge of themulti-application environment, a size of the second application windowwhile concurrently continuing to increase the size of the firstapplication window.
 17. The one or more computer-readable media asdescribed in claim 16, wherein the size of the second application windowis decreased until the size of second application window reaches aminimum window size of the second application window and the operationsfurther comprise ceasing, responsive to reaching the minimum window sizeof the second application window, to decrease the size of the secondapplication window while concurrently continuing to increase the size ofthe first application window such that the first application windowoverlaps the second application window.
 18. The one or morecomputer-readable media as described in claim 17, wherein the size ofthe first application window is increased until the joint dividerencounters the edge of the multi-application environment and theoperations further comprise relegating the second application window toa layer of the multi-application environment that is behind a layer onwhich the first application window resides.
 19. The one or morecomputer-readable media as described in claim 18, wherein the operationsfurther comprise restoring the size of the second application window toan original size or preferred size for the second application window.20. The one or more computer-readable media as described in claim 15,wherein the second application window is not in contact with an edge ofthe multi-application environment or a third application window.